View Issue Details

IDProjectCategoryView StatusLast Update
0001436K18X001.00 SKB SWANSW Issuepublic2022-03-11 10:41
Reporter(ALTech) Wooshin Kang Assigned To(ALTech) Wooshin Kang Due Date2022-02-28 11:57
PriorityurgentSeveritys3-moderateReproducibilityalways
Status closedResolutionfixed 
Summary0001436: No Audio in HLS vod.
DescriptionSKB have changed something for VOD some days ago. So now, HLS player is using for VOD playback.
If I set audio output to external device, I can't hear audio of VOD.
Can you check it ?
It looks like some change of volume table is root cause.

Please check also skb JIRA.

https://jira.skbroadband.com/browse/BTVV-4098
TagsNo tags attached.
Attach Tags

Users monitoring this issue

Activities

(ALTech) Wooshin Kang

2022-02-24 12:11

developer   ~0009500

I want to share some information for your debugging.
This is related with max volume level in volume table. If i change max value(-210) of DEFAULT_DEVICE_CATEGORY_SPEAKER_VOLUME_CURVE set to original value (-820), i can hear audio of VOD.

(SW) Bcan Yeh

2022-02-25 11:29

developer   ~0009507

Last edited: 2022-02-25 11:36

Hi Wooshin,

This issue is caused by a patch from Synaptics in jira SKBSBALT-140. (https://synaextjira.atlassian.net/browse/SKBSBALT-140)
You can check the patch from the attached picture.

While using -820, the inputted parameter "left" will be 0.389046. It could be processed by the patch.
While using -210, the inputted parameter "left" will be 0.785236. It is out of range and a default 0 will be used for volume.
That's why there is no sound.

We have already reopened jira SKBSBALT-140 and reported this issue.

1645759225480.jpg (192,510 bytes)   
1645759225480.jpg (192,510 bytes)   

(ALTech) Wooshin Kang

2022-03-02 15:22

developer   ~0009526

Hi Bcan,

Can you check below code ?

#if 1 //SKBSBALT-140
    left=(uint)(left*10000);
    
    if (left>=3800 && left<4000)volume=24; //btv32 -0.389046 =====> if (left>=3800)volume=24;
    if (left>=3000 && left<3800)volume=23; //btv31 -0.315865
    if (left>=2650 && left<3000)volume=22; //btv30 -0.270397

Thanks.

(SW) Bcan Yeh

2022-03-03 11:28

developer   ~0009534

Last edited: 2022-03-03 11:40

Hi Wooshin,

    We have some findings about this issue.
    1. The patch of SKBSBALT-140 is only workable for HLSPlayer.
        That means the volume of RTSPPlayer won't be affected by the patch.
        It is unnecessary to distinguish RTSPPlayer and HLSPlayer in this problem.
    2. While playing HLS content and being "NOT" passthrough, there will be no audio output in volume level 29/20/31/32.
        Because the parameter left is still out of the range of patch SKBSBALT-140.

    If the modification as you mentioned above is applied,
    1. the audio will be OK in HLS + passthrough.
    2. the vol 29/30/31/32 will be the same in HLS + non-passthrough.

   Our suggestion is to adjust patch SKBSBALT-140 for all volume levels and get better volume distribution.

   ps. We also updated this information in Synaptics jira SKBSBALT-140.

(SW) River Wong

2022-03-03 11:57

developer   ~0009535

Hi Wooshin,

I think the problem is caused by the patch of SKBSBALT-140 is based on old volume table to remapping the UI volume(0~32) to HLS volume(0~24). The patch of SKBSBALT-140 is applied on 2021/May.
But Jerry change the volume table based on speaker measurement on 2021/Aug. So, the patch of SKBSBALT-140 will not correctly mapping UI Volume to HLS volume.
I list the HLS volume and UI vol level for your reference.

1. HLS volume and UI Vol mapping based on 2021/Aug volume table. As you can see, UI Vol leve 32~29, the HLS volume=0.
Please note, the value of left is related to volume table. Synaptic's patch is based on old volume table to map UI Vol 32 level to 24 level. So as you can see, it is not mapping correctly because the patch is designed based on old volume table.
left=7852.000000 volume=0 //UI Vol Level 32
left=6194.000000 volume=0 //UI Vol Level 31
left=5188.000000 volume=0 //UI Vol Level 30
left=4345.000000 volume=0 //UI Vol Level 29
left=3639.000000 volume=23 //UI Vol Level 28
left=3044.000000 volume=23 //UI Vol Level 27
left=2549.000000 volume=21 //UI Vol Level 26
left=2135.000000 volume=20 //UI Vol Level 25
left=1788.000000 volume=19 //UI Vol Level 24
left=1410.000000 volume=18 //UI Vol Level 23
left=1141.000000 volume=16 //UI Vol Level 22
left=989.000000 volume=15 //UI Vol Level 21
left=827.000000 volume=14 //UI Vol Level 20
left=693.000000 volume=13 //UI Vol Level 19
left=580.000000 volume=12 //UI Vol Level 18
left=486.000000 volume=11 //UI Vol Level 17
left=406.000000 volume=11 //UI Vol Level 16
left=321.000000 volume=9 //UI Vol Level 15
left=269.000000 volume=8 //UI Vol Level 14
left=225.000000 volume=7 //UI Vol Level 13
left=188.000000 volume=6 //UI Vol Level 12
left=157.000000 volume=4 //UI Vol Level 11
left=132.000000 volume=4 //UI Vol Level 10
left=110.000000 volume=4 //UI Vol Level 9
left=92.000000 volume=3 //UI Vol Level 8
left=73.000000 volume=3 //UI Vol Level 7
left=61.000000 volume=3 //UI Vol Level 6
left=51.000000 volume=2 //UI Vol Level 5
left=42.000000 volume=2 //UI Vol Level 4
left=35.000000 volume=1 //UI Vol Level 3
left=30.000000 volume=1 //UI Vol Level 2
left=25.000000 volume=1 //UI Vol Level 1
left=0.000000 volume=0 //UI Vol Level 0

2. HLS volume and UI Vol mapping based on 2021/May volume table. As you can see, UI Vol 32 level correctly mapping to 24 HLS volume.
left=3890.000000 volume=24 //UI Vol Level 32
left=3158.000000 volume=23 //UI Vol Level 31
left=2703.000000 volume=22 //UI Vol Level 30
left=2312.000000 volume=21 //UI Vol Level 29
left=1976.000000 volume=20 //UI Vol Level 28
left=1690.000000 volume=19 //UI Vol Level 27
left=1447.000000 volume=18 //UI Vol Level 26
left=1237.000000 volume=17 //UI Vol Level 25
left=1058.000000 volume=16 //UI Vol Level 24
left=859.000000 volume=14 //UI Vol Level 23
left=734.000000 volume=13 //UI Vol Level 22
left=628.000000 volume=13 //UI Vol Level 21
left=537.000000 volume=12 //UI Vol Level 20
left=459.000000 volume=11 //UI Vol Level 19
left=393.000000 volume=10 //UI Vol Level 18
left=336.000000 volume=9 //UI Vol Level 17
left=287.000000 volume=8 //UI Vol Level 16
left=233.000000 volume=7 //UI Vol Level 15
left=199.000000 volume=6 //UI Vol Level 14
left=170.000000 volume=5 //UI Vol Level 13
left=146.000000 volume=4 //UI Vol Level 12
left=125.000000 volume=4 //UI Vol Level 11
left=106.000000 volume=4 //UI ol Level 10
left=91.000000 volume=3 //UI Vol Level 9
left=78.000000 volume=3 //UI Vol Level 8
left=63.000000 volume=3 //UI Vol Level 7
left=54.000000 volume=2 //UI Vol Level 6
left=46.000000 volume=2 //UI Vol Level 5
left=39.000000 volume=2 //UI Vol Level 4
left=34.000000 volume=1 //UI Vol Level 3
left=29.000000 volume=1 //UI Vol Level 2
left=24.000000 volume=1 //UI Vol Level 1
left=0.000000 volume=0 //UI Vol Level 0

Please also note, the passthrough mode and non-passthrough mode for HLS use the same volume table.

Just like Bcan said, the conclusion for solving this issue is to let Synaptics readjusts the patch based on current volume table.

(ALTech) Wooshin Kang

2022-03-04 12:22

developer   ~0009540

Hi River,

Patch is released by Synaptics. Please apply it.

https://jira.skbroadband.com/plugins/servlet/jeditor_file_provider?imgId=ckupload202203046843807324164369359&fileName=0001-SKBSBALT-140-adjust-volume-table29_32level.patch

thanks.

(SW) River Wong

2022-03-04 13:58

developer   ~0009541

Hi Wooshin,

patch is committed to bitbucket.

(SW) River Wong

2022-03-04 14:15

developer   ~0009542

Fixed by applying Synpatics's patch to adjust UI Vol 32~29 for VOID HLS.

/vendor/synaptics/vsxxx/
commit 4ca2f61ec34e0028f23e300e5420065aadb17a9b (HEAD)
Author: [시냅틱스] 박재민 <kail.park@synaptics.com>
Date: Fri Mar 4 12:10:55 2022 +0900

    adjust volume table29_32level

Issue History

Date Modified Username Field Change
2022-02-23 11:06 (ALTech) Wooshin Kang New Issue
2022-02-23 11:06 (ALTech) Wooshin Kang Status new => assigned
2022-02-23 11:06 (ALTech) Wooshin Kang Assigned To => (SW) River Wong
2022-02-23 11:06 (ALTech) Wooshin Kang Issue Monitored: (ALTech) Sangmin Choi
2022-02-23 11:06 (ALTech) Wooshin Kang Issue Monitored: (ALTech) SY Yoon
2022-02-23 14:50 (SW) River Wong Assigned To (SW) River Wong => (SW) Bcan Yeh
2022-02-24 12:11 (ALTech) Wooshin Kang Note Added: 0009500
2022-02-25 11:29 (SW) Bcan Yeh File Added: 1645759225480.jpg
2022-02-25 11:29 (SW) Bcan Yeh Note Added: 0009507
2022-02-25 11:36 (SW) Bcan Yeh Note Edited: 0009507
2022-03-02 15:22 (ALTech) Wooshin Kang Note Added: 0009526
2022-03-03 11:28 (SW) Bcan Yeh Note Added: 0009534
2022-03-03 11:40 (SW) Bcan Yeh Note Edited: 0009534
2022-03-03 11:57 (SW) River Wong Note Added: 0009535
2022-03-04 12:22 (ALTech) Wooshin Kang Note Added: 0009540
2022-03-04 13:58 (SW) River Wong Note Added: 0009541
2022-03-04 14:15 (SW) River Wong Assigned To (SW) Bcan Yeh => (ALTech) Wooshin Kang
2022-03-04 14:15 (SW) River Wong Status assigned => resolved
2022-03-04 14:15 (SW) River Wong Resolution open => fixed
2022-03-04 14:15 (SW) River Wong Note Added: 0009542
2022-03-07 10:36 (SW) Jacky Chiang Severity s2-severe => s3-moderate
2022-03-11 10:41 (SW) River Wong Status resolved => closed